Open
Conversation
9b2c119 to
30f7fc8
Compare
30f7fc8 to
21e0efb
Compare
Contributor
Author
|
oooops - sorry, didn't realize you were working on this :) Feel free to force-push again, and I'll go clean my apartment instead, like I should be doing… |
…ercion Use Arrow DataType Display style as the north-star: terse, readable type names instead of dumping internal Rust enum structure. - `dyn LogicalType`: delegates to NativeType Display instead of Debug, e.g. `Int32` instead of `LogicalType(Native(Int32), Int32)` - `TypeSignatureClass`: shows just the class name, e.g. `Numeric` instead of `TypeSignatureClass::Numeric` - `Coercion`: shows just the desired type, e.g. `Float64` instead of `Coercion(TypeSignatureClass::...)` - `ImplicitCoercion`: uses Display for its fields instead of Debug This dramatically improves error messages like: Before: `round(Coercion(TypeSignatureClass::Native(LogicalType(Native(Float64), Float64)), implicit_coercion=ImplicitCoercion([Numeric], default_type=Float64), ...)` After: `round(Float64, Int64)` Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
21e0efb to
aea6186
Compare
…n the snapshots, so just check the first part of the error message
timsaucer
approved these changes
Mar 1, 2026
Member
timsaucer
left a comment
There was a problem hiding this comment.
Very nice cleanup! I'll leave it open for one more working day in case anyone else wants to chime in.
Member
Contributor
|
I'll try take a look at this tomorrow |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Rationale for this change
Error messages should be friendly, short, and readable.
What changes are included in this PR?
Displayfordyn LogicalType,TypeSignature,TypeSignatureClass, andCoercioninstead of falling back toDebug{:?}(Debug) to{}(Display)non-nullprefix for non-nullable fields inNativeTypeDisplay, following Arrow's conventionThe north star is to follow the convention set by arrow-rs
Are these changes tested?
New snapshot tests have been introduced, and existing ones updated.
Are there any user-facing changes?
Yes!
Before
After
Before
After